chore(chart): disable Vault Kubernetes Injector#2692
Merged
migmartri merged 1 commit intochainloop-dev:mainfrom Feb 2, 2026
Merged
chore(chart): disable Vault Kubernetes Injector#2692migmartri merged 1 commit intochainloop-dev:mainfrom
migmartri merged 1 commit intochainloop-dev:mainfrom
Conversation
migmartri
approved these changes
Jan 30, 2026
Member
migmartri
left a comment
migmartri
left a comment
There was a problem hiding this comment.
thanks for your contribution, please make sure to signoff your commits, thanks
Filip7656
force-pushed
the
feat/disable-vault-injector
branch
from
cb0d083 to
80a849a
Compare
Signed-off-by: Filip Chlebowski <fchlebowski@gmail.com>
Filip7656
force-pushed
the
feat/disable-vault-injector
branch
from
80a849a to
854cfa9
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Disabling vault injector in development as we are not using it and it can cause problems because of mutatingwebhook resource.
In case that injector has problems communicating with vault it can stop all new pods (in whole cluster) from being deployed.
By default its better to disable it and if someone want to use it then he has to explicitly enable it.